Skip to content

Conversation

@mbgower
Copy link
Contributor

@mbgower mbgower commented Oct 3, 2025

Closes #246

change ARIA2 from sufficient for 3.3.1 to advisory
add ARIA2 as an advisory for 3.3.2
Revised the language to make it clearer why this technique is advisory.
@netlify
Copy link

netlify bot commented Oct 3, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit fe704cf
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/68e01d00ef9f1300082e672f
😎 Deploy Preview https://deploy-preview-4666--wcag2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@baldino-m
Copy link

baldino-m commented Oct 10, 2025

I don't get why, in the first line, "provide" has been replaced with "enhance": if a form field is visually identifiable as required (with an asterisk or whatever) and aria-required is required (pun not intended), then no programmatic information is given, so aria-required does actually provide some.

My understanding is also that, if the accessible name of the field contains some "required" wording, such as "First name (required)", then aria-required is redundant.

<p>Use of <code>aria-required="true"</code> might be beneficial even when an asterisk or other text symbol is programmatically associated with the field as it may reinforce its <code>required</code> property for some assistive technology users.</p>
<p>The fact that the element is required is often visually presented (such as a sign or symbol after the control). Using the <code>aria-required</code> property in addition to the visual presentation makes it much easier for user agents to pass on this important information to the user in a user agent-specific manner. Refer to <a href="https://www.w3.org/TR/html-aria/">ARIA in HTML</a> for information on how to provide WAI-ARIA States and Properties with HTML. WAI-ARIA States and Properties are compatible with other languages as well; refer to documentation in those languages. </p>
<p>This technique is set as advisory for meeting 3.3.2 Labels or Instructions, because use of <code>aria-required="true"</code> alone, without any visual indicator, would not be perceivable to most users.</p>
<p>However, when an asterisk or other text symbol is associated with the field, using the <code>aria-required</code> property in addition to the visual presentation makes it much easier for user agents to pass on this important information to the user in a user agent-specific manner. Refer to <a href="https://www.w3.org/TR/html-aria/">ARIA in HTML</a> for information on how to provide WAI-ARIA States and Properties with HTML. WAI-ARIA States and Properties are compatible with other languages as well; refer to documentation in those languages. </p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<p>However, when an asterisk or other text symbol is associated with the field, using the <code>aria-required</code> property in addition to the visual presentation makes it much easier for user agents to pass on this important information to the user in a user agent-specific manner. Refer to <a href="https://www.w3.org/TR/html-aria/">ARIA in HTML</a> for information on how to provide WAI-ARIA States and Properties with HTML. WAI-ARIA States and Properties are compatible with other languages as well; refer to documentation in those languages. </p>
<p>However, when an asterisk or other text symbol is associated with the field, using the <code>aria-required</code> property in addition to the visual presentation enables user agents to pass on this important information to the user in a user agent-specific manner. Refer to <a href="https://www.w3.org/TR/html-aria/">ARIA in HTML</a> for information on how to provide WAI-ARIA States and Properties with HTML. WAI-ARIA States and Properties are compatible with other languages as well; refer to documentation in those languages. </p>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Moving ARIA2 technique from 3.3.3 and putting in 3.3.2; adding ARIA21 to 3.3.3

4 participants